Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: target frameworks filtered to the supported ones only when applying a mapping #1523

Conversation

Mohamed-Hacene
Copy link
Collaborator

@Mohamed-Hacene Mohamed-Hacene commented Feb 20, 2025

Summary by CodeRabbit

  • New Features
    • Enhanced filtering capabilities for frameworks by leveraging compliance assessment criteria, allowing more refined queries.
    • Improved the framework selection experience on compliance assessment forms by passing relevant parameters to retrieve more accurate options.

Copy link
Contributor

coderabbitai bot commented Feb 20, 2025

Walkthrough

The pull request introduces three main changes. In the backend, a new attribute (fields_to_check) is added to the ComplianceAssessment class, and a new filter class (FrameworkFilter) with a corresponding filtering method is implemented to enhance framework filtering in the viewset. In the frontend, the ComplianceAssessmentForm is updated to include detailed URL parameters for the framework's autocomplete field.

Changes

File(s) Changes Summary
backend/core/models.py Added fields_to_check = ["name", "version"] to the ComplianceAssessment class.
backend/core/views.py Introduced a new filter class FrameworkFilter with a filter_framework method and updated FrameworkViewSet to use filterset_class = FrameworkFilter for enhanced filtering.
frontend/src/lib/components/Forms/ModelForm/ComplianceAssessmentForm.svelte Added the property optionsDetailedUrlParameters to the AutocompleteSelect component for the framework field, passing initialData.baseline as a URL parameter.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant FrameworkViewSet
    participant FrameworkFilter
    participant DB

    User->>FrameworkViewSet: GET /framework?baseline=value
    FrameworkViewSet->>FrameworkFilter: Apply filter_framework(queryset, name, value)
    FrameworkFilter->>DB: Query frameworks using baseline filter
    DB-->>FrameworkFilter: Return filtered frameworks
    FrameworkFilter-->>FrameworkViewSet: Return filtered queryset
    FrameworkViewSet-->>User: Respond with frameworks list
Loading

Possibly related PRs

Poem

I’m a rabbit, hopping through the code,
New fields and filters lighten the load.
With checks on "name" and "version" in view,
Frameworks now filter like morning dew.
Celebrate the change with a joyful leap—
Bugs, beware, for you must now sleep! 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
backend/core/views.py (1)

3116-3138: Optimize database queries and improve documentation.

The filter implementation is good but could be enhanced:

  1. Consider prefetching related fields to optimize database queries.
  2. Add docstring to explain the filter's purpose and behavior.

Apply this diff to improve the implementation:

 class FrameworkFilter(df.FilterSet):
+    """Filter for Framework objects based on baseline compliance assessment.
+    
+    Allows filtering frameworks that are either the selected baseline framework
+    or related to it through requirement mapping sets.
+    """
     baseline = df.ModelChoiceFilter(
         queryset=ComplianceAssessment.objects.all(),
         method="filter_framework",
         label="Baseline",
     )
 
     def filter_framework(self, queryset, name, value):
+        """Filter frameworks based on baseline compliance assessment.
+        
+        Args:
+            queryset: The base queryset of Framework objects.
+            name: The name of the filter field.
+            value: The ComplianceAssessment object to use as baseline.
+            
+        Returns:
+            QuerySet: Filtered queryset containing the baseline framework and
+                     frameworks related through requirement mapping sets.
+        """
         if not value:
             return queryset
         source_framework = value.framework
-        target_framework_ids = list(
-            RequirementMappingSet.objects.filter(
-                source_framework=source_framework
-            ).values_list("target_framework__id", flat=True)
-        )
+        # Optimize by using select_related to prefetch source_framework
+        target_framework_ids = RequirementMappingSet.objects.filter(
+            source_framework=source_framework
+        ).select_related('source_framework').values_list(
+            "target_framework__id", flat=True
+        )
         target_framework_ids.append(source_framework.id)
         return queryset.filter(id__in=target_framework_ids)
🧰 Tools
🪛 Ruff (0.8.2)

3136-3136: Framework may be undefined, or defined from star imports

(F405)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cc9fa71 and f33bfdb.

📒 Files selected for processing (3)
  • backend/core/models.py (1 hunks)
  • backend/core/views.py (1 hunks)
  • frontend/src/lib/components/Forms/ModelForm/ComplianceAssessmentForm.svelte (1 hunks)
🧰 Additional context used
🪛 Ruff (0.8.2)
backend/core/views.py

3136-3136: Framework may be undefined, or defined from star imports

(F405)


3145-3145: Framework may be undefined, or defined from star imports

(F405)

⏰ Context from checks skipped due to timeout of 90000ms (11)
  • GitHub Check: startup-functional-test (3.12)
  • GitHub Check: startup-docker-compose-test
  • GitHub Check: enterprise-startup-functional-test (3.12)
  • GitHub Check: functional-tests (3.12, chromium)
  • GitHub Check: enterprise-functional-tests (3.12, chromium)
  • GitHub Check: ruff (3.12)
  • GitHub Check: test (3.12)
  • GitHub Check: enterprise-startup-docker-compose-test
  • GitHub Check: build (3.12)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (3)
frontend/src/lib/components/Forms/ModelForm/ComplianceAssessmentForm.svelte (1)

72-72: LGTM! Good enhancement to framework filtering.

The addition of optionsDetailedUrlParameters to pass the baseline value enables server-side filtering of frameworks, which is more efficient than client-side filtering.

backend/core/models.py (1)

2850-2850: LGTM! Good addition for data validation.

The fields_to_check attribute specifies which fields should be validated for consistency or uniqueness, helping maintain data integrity for compliance assessments.

backend/core/views.py (1)

3140-3147: LGTM! Good use of custom filter class.

The change from filterset_fields to filterset_class = FrameworkFilter is a good improvement that enables more complex filtering capabilities.

🧰 Tools
🪛 Ruff (0.8.2)

3145-3145: Framework may be undefined, or defined from star imports

(F405)

@ab-smith ab-smith changed the title fix: framework filtering with baseline fix: target frameworks filtered to the supported ones only when applying a mapping Feb 20, 2025
@ab-smith ab-smith merged commit 0ffecf5 into main Feb 20, 2025
21 checks passed
@ab-smith ab-smith deleted the CA-869-Framework-are-not-filtered-anymore-when-creating-a-mapping branch February 20, 2025 20:09
@github-actions github-actions bot locked and limited conversation to collaborators Feb 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants